#: 593319 S0/Outbox File
    18-Jul-89  16:39:00
Sb: BOOT Prom Problems 
Fm: NOVSOFT REP 5455 
To: Brian L. Heess SMS 75470,565

Brian-
 
The biggest problem I've run into with multiple boot files is with the
autoexec. Each boot file has it's own autoexec until the shell gets
loaded(net3 or anet3), then they all have to use the same autoexec.bat in
sys:login.  Once you're in the LOGIN autoexec, you have to have some way to
determine which boot file you came from. Something like:
  autoexec.bat in boot file #1     autoexec in boot file #2
    set BOOT=1                        set BOOT=2
    ipx                               ipx
    net3                              net3
 
  autoexec in sys:login
    set BOOT=0
    ipx
    net3
    goto INST%BOOT%
    :INST1
    Echo hi, i'm boot file #1
    login
    goto end
    :INST2
    Echo hi, i'm boot file #2
    login
    goto end
    :end
 
This method works as long as you keep the net3 at the same byte position in
all of the boot files.  Most of the time, that's a pain.
 
The best way I've come across is to use a utility that comes with
LanMaster's boot proms.  This utility modifies the net3 so that DOS
continues with a different autoexec.bat file in sys:login.  Thus, you would
modify the net3 for boot file #1 to continue with AUTOEXE1.BAT in SYS:LOGIN
and the net3 for boot file #2 to continue with AUTOEXE2.BAT in SYS:LOGIN.
Then, when you DOSGENed #1, you'd copy #1's autoexec.bat to
SYS:LOGIN\AUTOEXE1.BAT and for #2, you'd copy #2's autoexec.bat to
SYS:LOGIN\AUTOEXE2.BAT.  BTW, I've had great luck with LanMaster's boot
proms and their support. I don't have their phone# handy but they advertise
fairly regularly in LanTimes.  They also go by LanWorks.
 
Hope this helps.  As you well know, boot proms are great when they work and
the s***s when they don't.
 
-Mark       

LanMaster Phone#1-800-441-6189 (Div of Vestra-Subco)
If all you want is their utility to modify the WS shell, order one of
any of their v2.1 boot proms.

Addt'l notes:

If you use LanMaster's utility to modify the shell, multiple boot files
are very effective and reasonable to maintain.

Besides using multiple boot files for different NIC types 
(ex. Arcnet&Ethernet), I've also used them very successfully for
loading Fresh Technologies Printer Assist to use a local printer
as a network printer.

Any parameters set in SHELL.CFG for IPX and NET3 are read from the SHELL.CFG
in the boot file -- SHELL.CFG need not be present in SYS:LOGIN.
Except for NETBIOS -- it reads SHELL.CFG _after_ net3 and therefore uses the
SHELL.CFG in SYS:LOGIN.

I strongly reccomend that the group EVERYONE be given ROS rights to 
SYS:LOGIN. This allows you to login from the autoexec.bat file and
not get the annoying "batch file not found" message.

Here's a sample autoexec.bat file that forces login on one server in a 
multiple server environment.  Note that the contents of all server's
SYS:LOGIN are identical. Also the the setting of COMSPEC _before_ IPX is
loaded. Even though drive Y: does not exist yet, this won't cause a problem
since the set value won't be used.

@Echo Off
Ver
Echo.
Rem type it out so we can check it without going back to the boot disk
Type config.sys
Echo.
SET COMSPEC=Y:COMMAND.COM
IPX
NET3
F:
rem force login to server RBC no matter which server we're on.
LOGIN RBC/


For the case of loading Printer Assist, I would have two boot files:

  NET$DOS.SYS   plain jane, uses above autoexec.bat, net3 modified
                to continue with AUTO_DOS.bat in SYS:LOGIN

  NET$PA.SYS    loads printer assist, net3 modified to continue with
                AUTO_PA.bat in sys:login

  NET$386.SYS   loads 386 to the max, net3 modified to continue with
                AUTO_386.bat in SYS:LOGIN


autoexec.bat in NET$PA.SYS and auto_pa.bat in SYS:LOGIN

  @Echo Off
  Ver
  Echo.
  Rem type it out so we can check it without going back to the boot disk
  Type config.sys
  Echo.
  SET COMSPEC=Y:COMMAND.COM
  IPX
  NET3
  F:
  LOGIN RBC/PRINTER_ASSIST
  PA/q1=LASER
  rem pause so that printing will occur immediately after power up
  rem (sitting in LOGIN waiting for a user name seems to cause problems)
  Echo Hit any key to login
  pause >nul
  rem force login to server RBC no matter which server we're on.
  LOGIN RBC/